Business Requirements Document (BRD)

Oracle Fusion Cloud — Inventory Management

Solar Panel Inventory | Energix USA | Construction Phase

Table of Contents

1. Executive Summary
2. Background & Context
3. Current State — As-Is
4. Objectives & Success Criteria
5. Scope
6. Stakeholders
7. Future State — End-to-End Process
8. Detailed Business Requirements
9. Integration Architecture
10. Data Migration Approach
11. Fit-Gap Analysis
12. Oracle Configuration Highlights
13. Assumptions & Dependencies
14. Open Issues & Decision Log
15. Glossary

1. Executive Summary

Energix USA is a utility-scale solar energy company currently in active Construction Phase operations across multiple project sites in the United States. Solar panels — the highest-value inventory items — are procured, stored at a third-party warehouse (Thyssenkrupp), and shipped to construction sites as needed. Today, all material tracking occurs outside Oracle Fusion, with only financial values manually reported. This creates significant inventory exposure, cost inaccuracies, and financial blind spots.

Oracle Fusion Inventory was partially configured in 2023 but never operationalized. Existing item master records and subinventory structures must be carefully preserved and extended — not rebuilt.

This BRD defines the To-Be solution, covering:

• A clean, maintainable material & lot structure aligned to Thyssenkrupp's pallet identifiers
• Reliable beginning balances loaded via FBDI following physical counts
• Warehouse-driven inventory movements — Thyssenkrupp's WMS pushes events to Oracle via API; Oracle records and does not initiate
• Financial inventory visibility by location and summarized, accounting for multiple POs and prices per item
• Automatic project cost accounting triggered by material movement events
• Nightly reconciliation between Oracle on-hand quantities and Thyssenkrupp WMS data

The solution is designed to maximize automation and minimize manual data entry, with Oracle as the system of record and Thyssenkrupp WMS as the operational source of physical movement truth.

2. Background & Context

2.1 Energix Project Phases

Energix solar projects follow three distinct phases. This document covers Construction Phase only.

2.2 Why Solar Panels?

Solar panels are the highest-value inventory item during construction. They are:

• Purchased in bulk under a Master Service Agreement (MSA) with First Solar via Blanket Purchase Orders
• Stored at Thyssenkrupp's third-party warehouse prior to site delivery
• Lot-controlled at pallet level — each pallet carries a unique Lot # and manufacturer part number
• Tracked by Thyssenkrupp in their WMS with full lot, pallet, and origin data accessible via REST API
• Capitalized as project costs upon delivery to site

2.3 Historical Context

3. Current State — As-Is

3.1 Pain Points Summary

3.2 Current Procurement & Delivery Flows (As-Is)

4. Objectives & Success Criteria

4.1 Core Objectives

4.2 Success Criteria

5. Scope

5.1 In Scope / Out of Scope

6. Stakeholders

7. Future State — End-to-End Process

7.1 Process Overview

The redesigned process is built on a warehouse-driven model. Oracle does not initiate or manage physical movements — Thyssenkrupp's WMS owns physical operations and pushes events to Oracle via API. Oracle records, costs, and reports.

7.2 Key Design Principle — WMS-Driven Shipment

Oracle does not initiate shipments. Thyssenkrupp WMS is the system of truth for physical panel movements. When panels leave the warehouse, the WMS API pushes the event — including the specific Pallet ID — to Oracle via OIC. Oracle records, costs, and reports.

This eliminates:

• Internal Transfer Order creation in Oracle by the PM
• FIFO or any Oracle-side picking logic
• Manual lot/pallet data entry

7.3 Pallet ID Tracking

Thyssenkrupp's WMS determines which specific pallet(s) physically leave the warehouse. The API sends the exact Pallet ID to Oracle. Oracle records this as the Lot number for that movement — there is no FIFO logic or picking selection inside Oracle.

8. Detailed Business Requirements

BR-01 — Material & Lot Structure

Priority: High | Actor: ERP Manager / Oracle Functional Consultant

Requirement:
Maintain and extend the existing Oracle Fusion item master for solar panels. The lot structure must align precisely with Thyssenkrupp's pallet-based tracking system.

Business Rules:

• Lot # must equal Pallet ID as assigned by Thyssenkrupp WMS.
• Manufacturer Part No. must match Thyssenkrupp records exactly.
• Lot DFF stores: Origin, pallet attributes, and other tracking attributes.
• Existing item master records must not be deleted or recreated — validate and correct in place.
• Pallet-to-Each UOM conversions must be validated per module type before go-live.

BR-02 — Beginning Balance Loading

Priority: Critical | Actor: Material Controller / ERP Manager

Requirement:
Establish reliable beginning balances in Oracle Fusion Inventory using physical count data. Balances are loaded via FBDI in three cycles.

Existing Inventory Handling:

Business Rules:

• Both physical counts must produce FBDI-ready files.
• Final pre-go-live count supervised by Energix personnel on-site.
• Immediate count must begin as soon as possible — this is on the critical path.

BR-03 — Receiving at 3PL Warehouse

Priority: High | Actor: PM / Planner, OIC Integration

Requirement:
When panels arrive at Thyssenkrupp's warehouse, the receipt is recorded in Oracle against the relevant PO. Lot and pallet data are auto-populated from Thyssenkrupp's WMS API — no manual entry.

Business Rules:

• Receipt executed as a bulk receipt against the PO in Oracle.
• Lot ID and Pallet ID are auto-populated from the Thyssenkrupp WMS API — no re-keying.
• Receipt posted to FG-Construction subinventory.
• Direct-to-site PO receipts carry project reference; 3PL receipts have no project reference.
• Minimum 3-business-day turnaround from Thyssenkrupp for prerequisite data.

BR-04 — Shipment from 3PL to Project Site (WMS-Driven)

Priority: High | Actor: Thyssenkrupp WMS (initiator), OIC, Oracle Fusion

Requirement:
When panels are physically shipped from Thyssenkrupp's warehouse to a project site, the Thyssenkrupp WMS pushes the shipment event to Oracle via OIC API. Oracle records the inventory movement and project cost transaction. The PM does not initiate a request in Oracle — the physical shipment drives the Oracle transaction.

Business Rules:

• Oracle does not initiate the shipment — Thyssenkrupp WMS pushes the event.
• The specific Pallet ID sent by the WMS API is recorded as the Lot on the Oracle inventory movement — no FIFO or Oracle-side picking logic.
• All movements in FG-Construction subinventory are recorded in Costing SLA (EPC Company segment).
• All project-related movements are recorded in Project SLA as project costs.
• Panels are capitalized to the project upon shipment confirmation.

BR-05 — Financial Inventory View

Priority: High | Actor: Finance, Material Controller

Requirement:
Because the same solar panel item is purchased across multiple POs at different prices, Energix requires a financial inventory report that provides:

1. Inventory value by location — on-hand quantity and value per subinventory / locator, showing the price at which each lot was received (linked to the originating PO).
2. Summarized financial view — total inventory value across all locations, grouped by item, with weighted average or actual cost depending on the costing method agreed with Finance.

Business Rules:

• Each lot (Pallet ID) must be linked to its originating PO and the unit price on that PO.
• The financial view must reflect different prices across POs for the same item.
• Report must be updated at minimum daily (after nightly reconciliation).
• Costing method (actual vs weighted average) to be agreed with Finance — see OI-02.
• Report must be accessible to Finance and Material Controller roles.

Acceptance Criteria:

• Report 1 (by location) shows item, lot/pallet, location, quantity, PO price, and inventory value.
• Report 2 (summarized) shows item, total quantity, total value across all locations.
• Both reports available in Oracle and exportable.
• Values reconcile to AP invoice amounts for the same lot/PO.

BR-06 — Consumption & Leftover Handling

Priority: High | Actor: Finance, Material Controller

Requirement:
Panels issued to a project are capitalized. At project close-out, leftovers must be handled per Finance and Legal guidance (pending — see OI-01).

BR-07 — Nightly Reconciliation

Priority: High | Actor: OIC (automated), Material Controller

Requirement:
A nightly OIC job compares Oracle on-hand quantities against Thyssenkrupp WMS quantities and alerts the Material Controller on any discrepancy.

Business Rules:

• Reconciliation runs nightly without manual intervention.
• Comparison is at Item + Lot (Pallet ID) + Location level.
• Material Controller must resolve discrepancies within 3 business days.
• Daily report generated regardless of outcome.

BR-08 — Annual Physical Count

Priority: Medium | Actor: Thyssenkrupp (execution), Material Controller (oversight)

Requirement:
Annual physical count at Thyssenkrupp performed by Thyssenkrupp under Energix Material Controller's supervision. Results reviewed and posted in Oracle.

Business Rules:

• Count covers Items, Subinventories, and Locators.
• Results reviewed and approved by Material Controller before posting.
• Standard Oracle Fusion Cycle Count / Physical Inventory process used.

9. Integration Architecture

9.1 System Landscape

9.2 Integration Interfaces

10. Data Migration Approach

10.1 Migration Process

10.2 FBDI Load Phases

10.3 Existing Inventory Handling

11. Fit-Gap Analysis

12. Oracle Configuration Highlights

12.1 Inventory Organization

12.2 Subinventory Structure

12.3 Item Attributes

12.4 Procurement

12.5 Accounting

13. Assumptions & Dependencies

14. Open Issues & Decision Log

15. Glossary

Document prepared by Energix IT — Oracle Fusion Practice
Version 2.0 | May 2026 | Draft — Pending Approval: Zvi & Tanya — Tuesday Session